Checklist: Installing a Generic Service resource

	Step	Reference
	Review server cluster resources.	Server cluster resources
	Review resource groups and resource dependencies.	Groups
	Plan common resource settings.	Checklist: Creating a new resource
	Note the exact service name as it appears in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.	The documentation for your service.
	Note the startup parameters of your service.	The documentation for your service.
	Ensure that the service is installed on all nodes.	Not applicable
	Determine which service registry keys need to be replicated on all nodes. Information on registry key replication Server clusters provides the ability for Generic Service and Generic Application resource types to specify registry keys below HKEY_LOCAL_MACHINE that need to be replicated to all nodes in the cluster. Some services or applications may update registry information while they are running by use of Win32 registry functions. The Cluster service provides registry checkpointing for noncluster-aware applications that may use these functions. Registry checkpointing for these resources occurs under the following conditions: When you specify a new registry key for the resource, the specified key is checkpointed. When the resource goes online, the registry keys are updated with the previously checkpointed information. When the resource is brought offline, all the checkpoints associated with this resource are saved. When the resource is online, and changes are made to the registry key that is registered with the cluster server for replication, the Cluster service ensures that the updates are written to a checkpoint maintained on the quorum device. If you manually update these registry keys while the application or service is offline, the changes may not be replicated or may be lost. To prevent this from happening, make any manual changes while the service or application resource is online. Cluster-aware applications need to make use of cluster registry functions as provided in the cluster application program interface (API) set when working with Cluster registry keys under HKEY_LOCAL_MACHINE. Refer to the Windows Clustering documentation in the Platform Software Development Kit (SDK) for more information on this topic.	The documentation for your service. Checklist: Installing a Generic Application resource
	Determine whether a dependent network name needs to be substituted for the computer name. Applications can make application program interface (API) calls to determine the name of the computer on which they are running. Making the generic application dependent on a network name resource causes the Use Network Name check box in Cluster Administrator to be selected. In such a case, the network name is returned instead of the computer name when the application makes the API call. Thus, applications that are not cluster aware continue to appear to be running on the same computer even after they move to a different cluster node.	The documentation for your application.
	Determine whether any application-specific registry keys need to be replicated on all cluster nodes. This pertains to applications that are not cluster aware. An application may store data in the registry. If the application is moved, but the registry data is not moved with it, the application's state is lost. If the cluster administrator specifies the root of the registry key, it enables the Cluster service to "watch" that key. The Cluster service captures the data in the key and any changes that occur. When the generic application resource is moved, the Cluster service moves the registry data to the new resource host and then brings the generic application resource online.	The documentation for your application.
	Use the New Resource Wizard to create the resource.	To create a new resource

Step

Reference

Review server cluster resources.

Server cluster resources

Review resource groups and resource dependencies.

Groups

Plan common resource settings.

Checklist: Creating a new resource

Note the exact service name as it appears in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

The documentation for your service.

Note the startup parameters of your service.

The documentation for your service.

Ensure that the service is installed on all nodes.

Not applicable

Determine which service registry keys need to be replicated on all nodes.

Information on registry key replication

Server clusters provides the ability for Generic Service and Generic Application resource types to specify registry keys below HKEY_LOCAL_MACHINE that need to be replicated to all nodes in the cluster.

Some services or applications may update registry information while they are running by use of Win32 registry functions. The Cluster service provides registry checkpointing for noncluster-aware applications that may use these functions. Registry checkpointing for these resources occurs under the following conditions:

When you specify a new registry key for the resource, the specified key is checkpointed.
When the resource goes online, the registry keys are updated with the previously checkpointed information.
When the resource is brought offline, all the checkpoints associated with this resource are saved.
When the resource is online, and changes are made to the registry key that is registered with the cluster server for replication, the Cluster service ensures that the updates are written to a checkpoint maintained on the quorum device.

If you manually update these registry keys while the application or service is offline, the changes may not be replicated or may be lost. To prevent this from happening, make any manual changes while the service or application resource is online.

Cluster-aware applications need to make use of cluster registry functions as provided in the cluster application program interface (API) set when working with Cluster registry keys under HKEY_LOCAL_MACHINE. Refer to the Windows Clustering documentation in the Platform Software Development Kit (SDK) for more information on this topic.

The documentation for your service.

Checklist: Installing a Generic Application resource

Determine whether a dependent network name needs to be substituted for the computer name.

Applications can make application program interface (API) calls to determine the name of the computer on which they are running. Making the generic application dependent on a network name resource causes the Use Network Name check box in Cluster Administrator to be selected. In such a case, the network name is returned instead of the computer name when the application makes the API call. Thus, applications that are not cluster aware continue to appear to be running on the same computer even after they move to a different cluster node.

The documentation for your application.

Determine whether any application-specific registry keys need to be replicated on all cluster nodes.

This pertains to applications that are not cluster aware. An application may store data in the registry. If the application is moved, but the registry data is not moved with it, the application's state is lost. If the cluster administrator specifies the root of the registry key, it enables the Cluster service to "watch" that key. The Cluster service captures the data in the key and any changes that occur. When the generic application resource is moved, the Cluster service moves the registry data to the new resource host and then brings the generic application resource online.

The documentation for your application.

Use the New Resource Wizard to create the resource.

To create a new resource